<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>7.3. The Front Controller</title>
<link rel="stylesheet" href="dbstyle.css" type="text/css">
<meta name="generator" content="DocBook XSL Stylesheets V1.72.0">
<link rel="start" href="index.html" title="Programmer's Reference Guide">
<link rel="up" href="zend.controller.html" title="Chapter 7. Zend_Controller">
<link rel="prev" href="zend.controller.basics.html" title="7.2. Zend_Controller Basics">
<link rel="next" href="zend.controller.request.html" title="7.4. The Request Object">
<link rel="chapter" href="introduction.html" title="Chapter 1. Introduction to Zend Framework">
<link rel="chapter" href="zend.acl.html" title="Chapter 2. Zend_Acl">
<link rel="chapter" href="zend.auth.html" title="Chapter 3. Zend_Auth">
<link rel="chapter" href="zend.cache.html" title="Chapter 4. Zend_Cache">
<link rel="chapter" href="zend.config.html" title="Chapter 5. Zend_Config">
<link rel="chapter" href="zend.console.getopt.html" title="Chapter 6. Zend_Console_Getopt">
<link rel="chapter" href="zend.controller.html" title="Chapter 7. Zend_Controller">
<link rel="chapter" href="zend.currency.html" title="Chapter 8. Zend_Currency">
<link rel="chapter" href="zend.date.html" title="Chapter 9. Zend_Date">
<link rel="chapter" href="zend.db.html" title="Chapter 10. Zend_Db">
<link rel="chapter" href="zend.debug.html" title="Chapter 11. Zend_Debug">
<link rel="chapter" href="zend.dojo.html" title="Chapter 12. Zend_Dojo">
<link rel="chapter" href="zend.dom.html" title="Chapter 13. Zend_Dom">
<link rel="chapter" href="zend.exception.html" title="Chapter 14. Zend_Exception">
<link rel="chapter" href="zend.feed.html" title="Chapter 15. Zend_Feed">
<link rel="chapter" href="zend.filter.html" title="Chapter 16. Zend_Filter">
<link rel="chapter" href="zend.form.html" title="Chapter 17. Zend_Form">
<link rel="chapter" href="zend.gdata.html" title="Chapter 18. Zend_Gdata">
<link rel="chapter" href="zend.http.html" title="Chapter 19. Zend_Http">
<link rel="chapter" href="zend.infocard.html" title="Chapter 20. Zend_InfoCard">
<link rel="chapter" href="zend.json.html" title="Chapter 21. Zend_Json">
<link rel="chapter" href="zend.layout.html" title="Chapter 22. Zend_Layout">
<link rel="chapter" href="zend.ldap.html" title="Chapter 23. Zend_Ldap">
<link rel="chapter" href="zend.loader.html" title="Chapter 24. Zend_Loader">
<link rel="chapter" href="zend.locale.html" title="Chapter 25. Zend_Locale">
<link rel="chapter" href="zend.log.html" title="Chapter 26. Zend_Log">
<link rel="chapter" href="zend.mail.html" title="Chapter 27. Zend_Mail">
<link rel="chapter" href="zend.measure.html" title="Chapter 28. Zend_Measure">
<link rel="chapter" href="zend.memory.html" title="Chapter 29. Zend_Memory">
<link rel="chapter" href="zend.mime.html" title="Chapter 30. Zend_Mime">
<link rel="chapter" href="zend.openid.html" title="Chapter 31. Zend_OpenId">
<link rel="chapter" href="zend.paginator.html" title="Chapter 32. Zend_Paginator">
<link rel="chapter" href="zend.pdf.html" title="Chapter 33. Zend_Pdf">
<link rel="chapter" href="zend.registry.html" title="Chapter 34. Zend_Registry">
<link rel="chapter" href="zend.rest.html" title="Chapter 35. Zend_Rest">
<link rel="chapter" href="zend.search.lucene.html" title="Chapter 36. Zend_Search_Lucene">
<link rel="chapter" href="zend.server.html" title="Chapter 37. Zend_Server">
<link rel="chapter" href="zend.service.html" title="Chapter 38. Zend_Service">
<link rel="chapter" href="zend.session.html" title="Chapter 39. Zend_Session">
<link rel="chapter" href="zend.soap.html" title="Chapter 40. Zend_Soap">
<link rel="chapter" href="zend.test.html" title="Chapter 41. Zend_Test">
<link rel="chapter" href="zend.text.html" title="Chapter 42. Zend_Text">
<link rel="chapter" href="zend.timesync.html" title="Chapter 43. Zend_TimeSync">
<link rel="chapter" href="zend.translate.html" title="Chapter 44. Zend_Translate">
<link rel="chapter" href="zend.uri.html" title="Chapter 45. Zend_Uri">
<link rel="chapter" href="zend.validate.html" title="Chapter 46. Zend_Validate">
<link rel="chapter" href="zend.version.html" title="Chapter 47. Zend_Version">
<link rel="chapter" href="zend.view.html" title="Chapter 48. Zend_View">
<link rel="chapter" href="zend.xmlrpc.html" title="Chapter 49. Zend_XmlRpc">
<link rel="appendix" href="requirements.html" title="Appendix A. Zend Framework Requirements">
<link rel="appendix" href="coding-standard.html" title="Appendix B. Zend Framework Coding Standard for PHP">
<link rel="appendix" href="copyrights.html" title="Appendix C. Copyright Information">
<link rel="index" href="the.index.html" title="Index">
<link rel="subsection" href="zend.controller.front.html#zend.controller.front.overview" title="7.3.1. Overview">
<link rel="subsection" href="zend.controller.front.html#zend.controller.front.methods.primary" title="7.3.2. Primary Methods">
<link rel="subsection" href="zend.controller.front.html#zend.controller.front.methods.environment" title="7.3.3. Environmental Accessor Methods">
<link rel="subsection" href="zend.controller.front.html#zend.controller.front.methods.params" title="7.3.4. Front Controller Parameters">
<link rel="subsection" href="zend.controller.front.html#zend.controller.front.subclassing" title="7.3.5. Subclassing the Front Controller">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader"><table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">7.3. The Front Controller</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="zend.controller.basics.html">Prev</a> </td>
<th width="60%" align="center">Chapter 7. Zend_Controller</th>
<td width="20%" align="right"> <a accesskey="n" href="zend.controller.request.html">Next</a>
</td>
</tr>
</table></div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="zend.controller.front"></a>7.3. The Front Controller</h2></div></div></div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zend.controller.front.overview"></a>7.3.1. Overview</h3></div></div></div>
<p>
            <code class="code">Zend_Controller_Front</code> implements a <a href="http://www.martinfowler.com/eaaCatalog/frontController.html" target="_top">Front
                Controller pattern</a> used in <a href="http://en.wikipedia.org/wiki/Model-view-controller" target="_top">Model-View-Controller
                (MVC)</a> applications. Its purpose is to initialize the
            request environment, route the incoming request, and then dispatch
            any discovered actions; it aggregates any responses and returns them
            when the process is complete.
        </p>
<p>
            <code class="code">Zend_Controller_Front</code> also implements the <a href="http://en.wikipedia.org/wiki/Singleton_pattern" target="_top">Singleton
            pattern</a>, meaning only a single instance of it may be available at
            any given time. This allows it to also act as a registry on which
            the other objects in the dispatch process may draw.
        </p>
<p>
            <code class="code">Zend_Controller_Front</code> registers a <a href="zend.controller.plugins.html" title="7.10. Plugins">plugin broker</a> with
            itself, allowing various events it triggers to be observed by
            plugins. In most cases, this gives the developer the opportunity to
            tailor the dispatch process to the site without the need to extend
            the front controller to add functionality.
        </p>
<p>
            At a bare minimum, the front controller needs one or more paths to
            directories containing <a href="zend.controller.action.html" title="7.7. Action Controllers">action
                controllers</a> in order to do its work. A variety of methods
            may also be invoked to further tailor the front controller
            environment and that of its helper classes.
        </p>
<div class="note"><table border="0" summary="Note: Default Behaviour">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png"></td>
<th align="left">Default Behaviour</th>
</tr>
<tr><td align="left" valign="top">
<p>
                By default, the front controller loads the <a href="zend.controller.plugins.html#zend.controller.plugins.standard.errorhandler" title="7.10.5.2. Zend_Controller_Plugin_ErrorHandler">ErrorHandler</a>
                plugin, as well as the <a href="zend.controller.actionhelpers.html#zend.controller.actionhelpers.viewrenderer" title="7.8.4.7. ViewRenderer">ViewRenderer</a>
                action helper plugin. These are to simplify error handling and
                view renderering in your controllers, respectively.
            </p>
<p>
                To disable the <code class="code">ErrorHandler</code>, perform the following
                at any point prior to calling <code class="code">dispatch()</code>:
            </p>
<pre class="programlisting">&lt;?php
// Disable the ErrorHandler plugin:
$front-&gt;setParam('noErrorHandler', true);
            </pre>
<p>
                To disable the <code class="code">ViewRenderer</code>, do the following prior
                to calling <code class="code">dispatch()</code>:
            </p>
<pre class="programlisting">&lt;?php
// Disable the ViewRenderer helper:
$front-&gt;setParam('noViewRenderer', true);
            </pre>
</td></tr>
</table></div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zend.controller.front.methods.primary"></a>7.3.2. Primary Methods</h3></div></div></div>
<p>
            The front controller has several accessors for setting up its
            environment. However, there are three primary methods key to the
            front controller's functionality:
        </p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="zend.controller.front.methods.primary.getinstance"></a>7.3.2.1. getInstance()</h4></div></div></div>
<p>
                <code class="code">getInstance()</code> is used to retrieve a front
                controller instance. As the front controller implements a
                Singleton pattern, this is also the only means possible for
                instantiating a front controller object.
            </p>
<pre class="programlisting">&lt;?php
$front = Zend_Controller_Front::getInstance();
            </pre>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="zend.controller.front.methods.primary.setcontrollerdirectory"></a>7.3.2.2. setControllerDirectory() and addControllerDirectory</h4></div></div></div>
<p>
                <code class="code">setControllerDirectory()</code> is used to tell <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">the dispatcher</a>
                where to look for <a href="zend.controller.action.html" title="7.7. Action Controllers">action controller</a>
                class files.  It accepts either a single path or an associative
                array of module/path pairs.
            </p>
<p>
                As some examples:
            </p>
<pre class="programlisting">
// Set the default controller directory:
$front-&gt;setControllerDirectory('../application/controllers');

// Set several module directories at once:
$front-&gt;setControllerDirectory(array(
    'default' =&gt; '../application/controllers',
    'blog'    =&gt; '../modules/blog/controllers',
    'news'    =&gt; '../modules/news/controllers',
));

// Add a 'foo' module directory:
$front-&gt;addControllerDirectory('../modules/foo/controllers', 'foo');
            </pre>
<div class="note"><table border="0" summary="Note">
<tr>
<td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png"></td>
<th align="left">Note</th>
</tr>
<tr><td align="left" valign="top"><p>
                    If you use <code class="code">addControllerDirectory()</code> without a
                    module name, it will set the directory for the
                    <code class="code">default</code> module -- overwriting it if it already
                    exists.
                </p></td></tr>
</table></div>
<p>
                You can get the current settings for the controller directory
                using <code class="code">getControllerDirectory()</code>; this will return an
                array of module/directory pairs.
            </p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="zend.controller.front.methods.primary.dispatch"></a>7.3.2.3. dispatch()</h4></div></div></div>
<p>
                <code class="code">dispatch(Zend_Controller_Request_Abstract $request = null,
                    Zend_Controller_Response_Abstract $response = null)</code>
                does the heavy work of the front controller. It may optionally
                take a <a href="zend.controller.request.html" title="7.4. The Request Object">request
                    object</a> and/or a <a href="zend.controller.response.html" title="7.9. The Response Object">response object</a>,
                allowing the developer to pass in custom objects for each.
            </p>
<p>
                If no request or response object are passed in,
                <code class="code">dispatch()</code> will check for previously registered
                objects and use those or instantiate default versions to use in
                its process (in both cases, the HTTP flavor will be used as the
                default).
            </p>
<p>
                Similarly, <code class="code">dispatch()</code> checks for registered <a href="zend.controller.router.html" title="7.5. The Standard Router: Zend_Controller_Router_Rewrite">router</a> and <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">dispatcher</a>
                objects, instantiating the default versions of each if none is
                found.
            </p>
<p>
                The dispatch process has three distinct events:
            </p>
<div class="itemizedlist"><ul type="disc">
<li><p>Routing</p></li>
<li><p>Dispatching</p></li>
<li><p>Response</p></li>
</ul></div>
<p>
                Routing takes place exactly once, using the values in the
                request object when <code class="code">dispatch()</code> is called.
                Dispatching takes place in a loop; a request may either indicate
                multiple actions to dispatch, or the controller or a plugin may
                reset the request object to force additional actions to
                dispatch. When all is done, the front controller returns a
                response.
            </p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="zend.controller.front.methods.primary.run"></a>7.3.2.4. run()</h4></div></div></div>
<p>
                <code class="code">Zend_Controller_Front::run($path)</code> is a static
                method taking simply a path to a directory containing
                controllers. It fetches a front controller instance (via
                <a href="zend.controller.front.html#zend.controller.front.methods.primary.getinstance" title="7.3.2.1. getInstance()">getInstance()</a>,
                registers the path provided via <a href="zend.controller.front.html#zend.controller.front.methods.primary.setcontrollerdirectory" title="7.3.2.2. setControllerDirectory() and addControllerDirectory">setControllerDirectory()</a>,
                and finally <a href="zend.controller.front.html#zend.controller.front.methods.primary.dispatch" title="7.3.2.3. dispatch()">dispatches</a>.
            </p>
<p>
                Basically, <code class="code">run()</code> is a convenience method that can
                be used for site setups that do not require customization of the
                front controller environment.
            </p>
<pre class="programlisting">&lt;?php
// Instantiate front controller, set controller directory, and dispatch in one
// easy step:
Zend_Controller_Front::run('../application/controllers');
            </pre>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zend.controller.front.methods.environment"></a>7.3.3. Environmental Accessor Methods</h3></div></div></div>
<p>
            In addition to the methods listed above, there are a number of
            accessor methods that can be used to affect the front controller
            environment -- and thus the environment of the classes to which the
            front controller delegates.
        </p>
<div class="itemizedlist"><ul type="disc">
<li><p>
                    <code class="code">resetInstance()</code> can be used to clear all
                    current settings. Its primary purpose is for testing, but it
                    can also be used for instances where you wish to chain
                    together multiple front controllers.
                </p></li>
<li><p>
                    <code class="code">(set|get)DefaultControllerName()</code> let you
                    specify a different name to use for the default controller
                    ('index' is used otherwise) and retrieve the current value.
                    They proxy to <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">the
                        dispatcher</a>.
                </p></li>
<li><p>
                    <code class="code">(set|get)DefaultAction()</code> let you specify a
                    different name to use for the default action ('index' is
                    used otherwise) and retrieve the current value.  They proxy
                    to <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">the
                        dispatcher</a>.
                </p></li>
<li><p>
                    <code class="code">(set|get)Request()</code> let you specify <a href="zend.controller.request.html" title="7.4. The Request Object">the request</a>
                    class or object to use during the dispatch process and to
                    retrieve the current object. When setting the request
                    object, you may pass in a request class name, in which case
                    the method will load the class file and instantiate it.
                </p></li>
<li>
<p>
                    <code class="code">(set|get)Router()</code> let you specify <a href="zend.controller.router.html" title="7.5. The Standard Router: Zend_Controller_Router_Rewrite">the router</a>
                    class or object to use during the dispatch process and to
                    retrieve the current object. When setting the router
                    object, you may pass in a router class name, in which case
                    the method will load the class file and instantiate it.
                </p>
<p>
                    When retrieving the router object, it first checks to see if
                    one is present, and if not, instantiates the default router
                    (rewrite router).
                </p>
</li>
<li><p>
                    <code class="code">(set|get)BaseUrl()</code> let you specify <a href="zend.controller.request.html#zend.controller.request.http.baseurl" title="7.4.2.2. Base Url and Subdirectories">the base
                        URL</a> to strip when routing requests and to
                    retrieve the current value. The value is provided to the
                    request object just prior to routing.
                </p></li>
<li>
<p>
                    <code class="code">(set|get)Dispatcher()</code> let you specify <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">the
                        dispatcher</a> class or object to use during the
                    dispatch process and retrieve the current object. When
                    setting the dispatcher object, you may pass in a dispatcher
                    class name, in which case the method will load the class
                    file and instantiate it.
                </p>
<p>
                    When retrieving the dispatcher object, it first checks to see if
                    one is present, and if not, instantiates the default
                    dispatcher.
                </p>
</li>
<li><p>
                    <code class="code">(set|get)Response()</code> let you specify <a href="zend.controller.response.html" title="7.9. The Response Object">the response</a>
                    class or object to use during the dispatch process and to
                    retrieve the current object. When setting the response
                    object, you may pass in a response class name, in which case
                    the method will load the class file and instantiate it.
                </p></li>
<li><p>
                    <code class="code">registerPlugin(Zend_Controller_Plugin_Abstract $plugin, $stackIndex = null)</code>
                    allows you to register a <a href="zend.controller.plugins.html" title="7.10. Plugins">plugin objects</a>.
                    By setting the optional <code class="code">$stackIndex</code>, you can
                    control the order in which plugins will execute.
                </p></li>
<li><p>
                    <code class="code">unregisterPlugin($plugin)</code> let you 
                    unregister <a href="zend.controller.plugins.html" title="7.10. Plugins">plugin objects</a>.
                    <code class="code">$plugin</code> may be either a plugin object or a
                    string denoting the class of plugin to unregister.
                </p></li>
<li>
<p>
                    <code class="code">throwExceptions($flag)</code> is used to turn on/off
                    the ability to throw exceptions during the dispatch process.
                    By default, exceptions are caught and placed in the <a href="zend.controller.response.html" title="7.9. The Response Object">response
                        object</a>; turning on <code class="code">throwExceptions()</code>
                    will override this behaviour.
                </p>
<p>
                    For more information, read <a href="zend.controller.exceptions.html" title="7.12. MVC Exceptions">Section 7.12, “MVC Exceptions”</a>.
                </p>
</li>
<li>
<p>
                    <code class="code">returnResponse($flag)</code> is used to tell the front
                    controller whether to return the response
                    (<code class="code">true</code>) from <code class="code">dispatch()</code>, or if the
                    response should be automatically emitted
                    (<code class="code">false</code>).  By default, the response is
                    automatically emitted (by calling
                    <code class="code">Zend_Controller_Response_Abstract::sendResponse()</code>);
                    turning on <code class="code">returnResponse()</code> will override this
                    behaviour.
                </p>
<p>
                    Reasons to return the response include a desire to check for
                    exceptions prior to emitting the response, needing to log
                    various aspects of the response (such as headers), etc.
                </p>
</li>
</ul></div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zend.controller.front.methods.params"></a>7.3.4. Front Controller Parameters</h3></div></div></div>
<p>
            In the introduction, we indicated that the front controller also
            acts as a registry for the various controller components. It does so
            through a family of "param" methods. These methods allow you to
            register arbitrary data -- objects and variables -- with the front
            controller to be retrieved at any time in the dispatch chain. These
            values are passed on to the router, dispatcher, and action
            controllers. The methods include:
        </p>
<div class="itemizedlist"><ul type="disc">
<li><p>
                    <code class="code">setParam($name, $value)</code> allows you to set a
                    single parameter of <code class="code">$name</code> with value
                    <code class="code">$value</code>.
                </p></li>
<li><p>
                    <code class="code">setParams(array $params)</code> allows you to set
                    multiple parameters at once using an associative array.
                </p></li>
<li><p>
                    <code class="code">getParam($name)</code> allows you to retrieve a single
                    parameter at a time, using <code class="code">$name</code> as the
                    identifier.
                </p></li>
<li><p>
                    <code class="code">getParams()</code> allows you to retrieve the entire
                    list of parameters at once.
                </p></li>
<li><p>
                    <code class="code">clearParams()</code> allows you to clear a single
                    parameter (by passing a string identifier), multiple named
                    parameters (by passing an array of string identifiers), or the
                    entire parameter stack (by passing nothing).
                </p></li>
</ul></div>
<p>
            There are several pre-defined parameters that may be set that have
            specific uses in the dispatch chain:
        </p>
<div class="itemizedlist"><ul type="disc">
<li>
<p>
                    <code class="code">useDefaultControllerAlways</code> is used to hint to
                    <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">the
                        dispatcher</a> to use the default controller in the
                    default module for any request that is not dispatchable
                    (i.e., the module, controller, and/or action do not exist).
                    By default, this is off.
                </p>
<p>
                    See <a href="zend.controller.exceptions.html#zend.controller.exceptions.internal" title="7.12.3. MVC Exceptions You May Encounter">Section 7.12.3, “MVC Exceptions You May Encounter”</a>
                    for more detailed information on using this setting.
                </p>
</li>
<li><p>
                    <code class="code">disableOutputBuffering</code> is used to hint to <a href="zend.controller.dispatcher.html" title="7.6. The Dispatcher">the
                        dispatcher</a> that it should not use output
                    buffering to capture output generated by action controllers.
                    By default, the dispatcher captures any output and appends
                    it to the response object body content.
                </p></li>
<li><p>
                    <code class="code">noViewRenderer</code> is used to disable the <a href="zend.controller.actionhelpers.html#zend.controller.actionhelpers.viewrenderer" title="7.8.4.7. ViewRenderer">ViewRenderer</a>.
                    Set this parameter to true to disable it.
                </p></li>
<li><p>
                    <code class="code">noErrorHandler</code> is used to disable the <a href="zend.controller.plugins.html#zend.controller.plugins.standard.errorhandler" title="7.10.5.2. Zend_Controller_Plugin_ErrorHandler">Error
                        Handler plugin</a>. Set this parameter to true to
                    disable it.
                </p></li>
</ul></div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zend.controller.front.subclassing"></a>7.3.5. Subclassing the Front Controller</h3></div></div></div>
<p>
            To subclass the Front Controller, at the very minimum you will need
            to override the <code class="code">getInstance()</code> method:
        </p>
<pre class="programlisting">
class My_Controller_Front extends Zend_Controller_Front
{
    public static function getInstance()
    {
        if (null === self::$_instance) {
            self::$_instance = new self();
        }

        return self::$_instance;
    }
}

        </pre>
<p>
            Overriding the <code class="code">getInstance()</code> method ensures that
            subsequent calls to
            <code class="code">Zend_Controller_Front::getInstance()</code> will return an
            instance of your new subclass instead of a
            <code class="code">Zend_Controller_Front</code> instance -- this is particularly
            useful for some of the alternate routers and view helpers.
        </p>
<p>
            Typically, you will not need to subclass the front controller unless
            you need to add new functionality (for instance, a plugin
            autoloader, or a way to specify action helper paths). Some points
            where you may want to alter behaviour may include modifying how
            controller directories are stored, or what default router or
            dispatcher are used.
        </p>
</div>
</div>
<div class="navfooter"><table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="zend.controller.basics.html">Prev</a> </td>
<td width="20%" align="center"><a accesskey="u" href="zend.controller.html">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="zend.controller.request.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">7.2. Zend_Controller Basics </td>
<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
<td width="40%" align="right" valign="top"> 7.4. The Request Object</td>
</tr>
</table></div>
<div class="revinfo"></div>
</body>
</html>
